docs: use pGPU alias #2070
Merged
docs: use pGPU alias #2070
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Do the documentation changes need to be backported?Changes to
|
|
burgerdev
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, Contrast allowed GPU model-specific resource types (such as
nvidia.com/GH100_H100L_94GB) instead of the genericnvidia.com/pgputo support heterogeneous hardware configurations. However, as Kata upstream isn't supporting this, this is switched to setup the Nvidia operator with the pGPU alias instead. We might be able to revert to the resource specific annotations in the future, depending on the upstream support for it.As a user, follow the updated setup instructions for the Nvidia GPU operator and use
nvidia.com/pgpuin resource limit.